docs(tool-executions): follow the Logging Policy rename, and fix the API credential - #1157
Merged
Merged
Conversation
…that works The dashboard page is called Logging Policy now, and it sits under Organization, so "open your organization and select Execution Logging" names neither the label nor the path a reader would follow. The curl was worse than stale. It sent `$ARCADE_API_KEY`, which every other sample on the site means as a project key, and this endpoint refuses one: `401 Invalid credentials: missing account ID`. The policy is org-scoped and the route resolves an account, so a project key cannot carry the caller. Verified against a live stack — the same request with an account token returns 200. Everything else on the page was checked against that stack and holds: recording starts ALLOWED, the window starts at 7 with a maximum of 90 reported as `max_log_retention_days`, 0 and 91 are both refused with 422 rather than clamped, and sending one field leaves the other alone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follows ArcadeAI/monorepo#3670, which renamed the dashboard page from Execution Logging to Logging Policy.
Targets
add-doc-screenshotsbecause that is where the page lives — #1141 merged there and the branch has not reachedmainyet.Three changes
The rename. "Open your organization in the dashboard and select Execution Logging" named neither the current label nor the path. Now Organization → Logging Policy.
The endpoint URL, which was wrong from the start.
logging-configis a Coordinator route. Every other Coordinatororgs/call on this site iscloud.arcade.dev/api/v1/; only this page saidapi.arcade.dev/v1/. Against a live stack,/v1/orgs/...returns404and/api/v1/orgs/...resolves.A note on the credential. A project API key is refused here with
401 Invalid credentials: missing account ID— the route resolves an account, because the policy belongs to the organization rather than a project. The variable stays$ARCADE_API_KEY, matching the audit log page, which documents the same org-scoped shape as "User (API key/JWT)"; the added sentence just says a project key will not do.Verified against a live stack
Signed in as an org admin, walked the page, then exercised every factual claim through the API:
logging_data_retention = ALLOWEDdefault_log_retention_days = 7max_log_retention_days9042291→422200401Sidebar, breadcrumb and page heading all read Logging Policy for an org admin.
Two caveats
Generate LLMs.txtfails on this PR, and on every PR. It dies at checkout —could not read Username for 'https://github.com'— becausesecrets.DOCS_PUBLISHABLE_GH_TOKENresolves empty. Every run since 2026-08-26 18:43 has failed across three authors' branches. Unrelated to this change, but someone with repo admin should reissue that token.pnpm buildfails on this branch withModule not found: '@arcadeai/ui-kit/utils/attribution'inproxy.ts. Pre-existing — it fails identically with this change stashed — so the MDX here is not build-validated.Note on the second commit
8e7c9a33introduced$ARCADE_ACCOUNT_TOKEN, a variable that does not exist.7fba7342reverts it and fixes the URL. Reviewing the head commit is enough; the intermediate state is wrong.